home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
e
/
misc.save
/
000333_fdc@panix.com_Mon Mar 22 12:30:35 2010.msg
< prev
next >
Wrap
Text File
|
2011-07-03
|
3KB
|
58 lines
Path: reader1.panix.com!panix!not-for-mail
From: Frank da Cruz <fdc@panix.com>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Transferring files over SSH in the console
Date: Mon, 22 Mar 2010 16:27:51 +0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 41
Message-ID: <slrnhqf6k7.j4f.fdc@panix3.panix.com>
References: <880dece01003211552le9d6018odb9bd683c3c897a9@mail.gmail.com> <201003212314.32985.reidac@bellatlantic.net> <201003212325.49742.reidac@bellatlantic.net> <880dece01003220152p3c8d50e1le80fe6bab5522601@mail.gmail.com> <4BA76359.6090405@internode.on.net>
Reply-To: fdc@columbia.edu
NNTP-Posting-Host: panix3.panix.com
X-Trace: reader1.panix.com 1269275271 2521 166.84.1.3 (22 Mar 2010 16:27:51 GMT)
X-Complaints-To: abuse@panix.com
NNTP-Posting-Date: Mon, 22 Mar 2010 16:27:51 +0000 (UTC)
User-Agent: slrn/0.9.8.0 (NetBSD)
Xref: panix comp.protocols.kermit.misc:15936
On 2010-03-22, Arthur Marsh <arthur.marsh@internode.on.net> wrote:
: Dotan Cohen wrote, on 2010-03-22 19:22:
:
(a lot of stuff about transferring files over SSH in the console)
To put it simply, nothing could be easier than Kermit. I have an SSH
connection (from Windows, using Kermit 95, or from Unix using Kermit)
to a Unix shell session. Some of us still prefer to work this way;
we get more done :-)
The Unix host has C-Kermit stored as "kermit" in a directory that's
in the path. In my ~/.bashrc I have:
alias s="kermit -Ys"
alias g="kermit -Yg"
Any time I want to send a file from the host to my desktop I just
say "s xxx", where xxx is the name of the I want to send; it can also
contain wildcards to send multiple files a once.
Any time I want to retrieve a file from my desktop and put it on the Unix
host, I say "g xxx" -- same deal, except this time you have to be slightly
careful about wildcards because they are not (normally) to interpreted
on the Unix host, but rather on the desktop system.
What happens next, in both cases, is that the file or files is/are
transferred, poof. That's the whole thing, no more commands, no escaping back
and reconnecting, no complicated config files, no repitious and redundant
authentication. The files go over the connection you already have.
It doesn't matter if the files are text or binary, even if the two systems
differ as to file formats (e.g. Windows / Linux / VMS); Kermit chooses the
correct transfer mode for each file automatically.
Of course there are options if you want to get fancy, e.g.:
. Only transfer files that are newer than the counterparts on the other end.
. Convert character sets of text files appropriately (e.g. 8859-1 / UTF-8).
. Recover a partial transfer from the point of failure (binary mode only).
- Frank